Digital rights management integrated service solution

ABSTRACT

The present disclosure provides a system for accessing content secured according to differing digital rights management protocols. The system comprises a device that presents the content and a client component loaded on the device that uses and requests content according to a first digital rights management protocol. The system includes a first content server that receives a request for and provides content according to the first digital rights management protocol and a second content server that receives a request for and provides content according to a second digital rights management protocol. A mediation component maps requests and responses between the client component and the second content server, mediating between the first and second digital rights management protocols. The disclosure contemplates mediating between open digital rights language (ODRL) and extensible right markup language (XRML) digital rights management protocols as well as other digital rights management protocols.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 10/812,532, filed Mar. 30, 2004 now U.S. Pat. No.7,565,438 B1, issued Jul. 21, 2009 and entitled “Digital RightsManagement Integrated Service Solution,” which is incorporated herein byreference in its entirety for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

FIELD OF THE INVENTION

The present invention is directed to computer software, and moreparticularly, but not by way of limitation, to a system and method fordigital rights management.

BACKGROUND OF THE INVENTION

Traditional rights management of physical materials benefits from thephysical nature of the material being protected, as this provides somelimitation to the ease with which this content can be copied orotherwise stolen. Digital files, however, can be very easily copied, andalready copyright violations are widespread, as for example illegaldownloading of music files. Digital rights management (DRM) technologyaddresses the need to identify, protect, monitor, and track digitalmaterials and their use.

Several DRM protocols or standards have emerged to support secure,authorized access to digital materials including extensible rightsmarkup language (XrML), open digital rights language (ODRL), a Sonyproprietary content management protocol, and an Apple Computerproprietary content management protocol, just to name a few.

DRM protocols permit a device to download a digital file from a contentprovider and to access this file, for example a digital music file, afixed number of times within a fixed time window in exchange forcharging a fee to a credit card or to an account with the contentprovider. For example, an individual might download a song performed bya popular artist to an Internet enabled audio system for five plays overthe next seven days.

SUMMARY OF THE INVENTION

The present disclosure provides, according to one embodiment, a systemfor accessing content secured according to differing digital rightsmanagement protocols. The system comprises a device that presents thecontent, and a client software component loaded on the device that usesand requests content according to a first digital rights managementprotocol. The system includes a first content server that receives arequest for and provides content according to the first digital rightsmanagement protocol, and a second content server that receives a requestfor and provides content according to a second digital rights managementprotocol. A mediation component maps requests and responses between theclient software component and the second content server, mediatingbetween the first and second digital rights management protocols. Thedisclosure contemplates mediating between open digital rights languageand extensible right markup language protocols as well as other digitalrights management protocols.

In one embodiment, a system is provided for executing a computer programon a wireless mobile device by loading the computer program into thewireless mobile device, either wholly or in a sequence of segments, atthe time the wireless mobile device desires to execute the computerprogram. The system comprises a wireless communication network and anapplication server which receives a request for a segment of the programor the whole program and returns the segment of the program or the wholeprogram. The system also includes a mobile device which desires toexecute the computer program and requests that the application serverprovide a segment of the program or the whole program over the wirelesscommunication network. The wireless communication network may include abase transceiver station in radio communication with the wireless mobiledevice, a base station controller in communication with the basetransceiver station, and a mobile switching center in communication withthe base transceiver station. The mobile switching center is incommunication with either the public switched telephone network or thepacket data network. The application server attaches to the wirelessnetwork either through the packet data network or the public switchedtelephone network.

In one embodiment, a method is provided for executing a computer programon a wireless mobile device by loading the program into the wirelessmobile device, either wholly or in a sequence of segments, at the timethe wireless mobile device desires to execute the program. The methodcomprises downloading a part of the program to the wireless mobiledevice from the wireless network, executing the part of the program,downloading the next part of the program to the wireless mobile device,executing this next part of the program, and so on until as much of theprogram as is desired is executed.

In one embodiment, a system for accessing content according to any ofseveral content management protocols is disclosed. The system comprisesa first mobile device which can present content and a client softwarecomponent installed in the first mobile device which can use the contentaccording to a first content management protocol. The system alsoincludes a second mobile device which can present content and a clientsoftware component installed in the second mobile device which can usethe content according to a second content management protocol. Thesystem includes a multi-protocol content server in communication withthe first and second mobile devices which is able to receive contentrequests and provide content according to the several content managementprotocols.

These and other features and advantages will be more clearly understoodfrom the following detailed description taken in conjunction with theaccompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and theadvantages thereof, reference is now made to the following briefdescription, taken in connection with the accompanying drawings anddetailed description, wherein like reference numerals represent likeparts.

FIG. 1 is a block diagram that depicts digital rights management (DRM)clients in communication with DRM license servers and DRM contentservers.

FIG. 2 is a block diagram that depicts a DRM integrated access systemaccording to one embodiment.

FIG. 3 is a block diagram that depicts the DRM integrated access systemaccording to another embodiment.

FIG. 4 is a block diagram that depicts a system for loading computerprograms on demand from an application swap server to a wireless mobiledevice.

FIG. 5 is a flow chart that depicts a method for loading computerprograms on demand to the wireless mobile device.

FIG. 6 is a block diagram that depicts the DRM integrated access systemaccording to another embodiment.

FIG. 7 is a block diagram that depicts an exemplary general purposecomputer system suitable for implementing the several embodiments of thedisclosure.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

It should be understood at the outset that although an exemplaryimplementation of one embodiment of the present disclosure isillustrated below, the present system may be implemented using anynumber of techniques, whether currently known or in existence. Thepresent disclosure should in no way be limited to the exemplaryimplementations, drawings, and techniques illustrated below, includingthe exemplary design and implementation illustrated and describedherein.

Digital rights management (DRM) technology addresses the need toidentify, protect, monitor, and track digital materials and their use.Digital materials may be referred to as content and may include textcontent, audio content, video content, music content, audio/videocontent, and encrypted content. With several competing DRM standards orprotocols deployed to secure and manage access to content, the need fordevices to interoperate with different DRM protocols arises. Forexample, if a listener attempts to download a music audio to an ODRLbased playback device from a content provider who has chosen to protectand manage content using XrML, the attempt will fail. Intelligentdevices with large resources may be able to store DRM client programs tointeract with several prevalent DRM protocols concurrently. Mobiledevices or low cost devices, however, may have limited memory resourcesand may be capable of storing only one DRM client program supporting asingle DRM protocol.

Turning now to FIG. 1, a block diagram depicts the prior art for ODRLand XrML access to content. An ODRL client 12 is in communication withan ODRL license server 14 and with an ODRL content server 16. The ODRLclient 12 requests a content license or digital certificate from theODRL license server 14, and the ODRL license server 14 returns thelicense or digital certificate to the ODRL client 12. The ODRL client 12requests content from the ODRL content server 16, sending the license ordigital certificate encapsulated in this request. The ODRL contentserver 16 returns the content to the ODRL client 12 along with a rightsstatement. A rights statement describes the content access rightsgranted to the ODRL client 12 which may include details specifying howthe ODRL client 12 may use the content (view, copy, or print), how manytimes the ODRL client 12 may use the content, and a period of time overwhich these rights are granted to the ODRL client 12. The ODRL client 12consumes the content (viewing the content, playing the content, orotherwise using the content) and sends a usage report to the ODRLlicense server 14.

An XrML client 18 is in communication with an XrML license server 20 andwith an XrML content server 22. The XrML client 18 requests a contentlicense or digital certificate from the XrML license server 20, and theXrML license server 20 returns the license or digital certificate to theXrML client 18. The XrML client 18 requests content from the XrMLcontent server 22, sending the license or digital certificateencapsulated in this request. The XrML content server 22 returns thecontent to the XrML client 18 along with a rights statement describingthe content access rights granted to the XrML client 18. The XrML client18 consumes the content and sends a usage report to the XrML licenseserver 20.

At this level of detail, the general interactions to obtain access tocontent are similar. However, the ODRL client 12 is not able to accessthe XrML content managed by the XrML content server 22, and the XrMLclient 18 is not able to access ODRL content managed by the ODRL contentserver 16 due to incompatibilities between the two protocols. Similarincompatibilities may prevent interoperation among other DRM standardsor protocols.

Turning now to FIG. 2, a DRM integrated access system 50 is depicted.The present disclosure may employ multiple license servers, such as afirst license server and a second license server, where for example, thefirst license server may be the ODRL license server 14 and the secondlicense server may be the XrML license server 20. It will be appreciatedhowever that the other types and/or combinations of license servers maybe used as well. A translation server 52, which may also be referred toas a mediation component, is in communication with the ODRL client 12,the ODRL license server 14, the ODRL content server 16, the XrML client18, the XrML license server 20, and the XrML content server 22. Thetranslation server 52 is operable to map, translate, or mediate requestsfor content according to a first content management protocol into arequest for content according to a second content management protocol.The translation server 52 is further operable to map, translate, ormediate responses according to the second content management protocolinto responses according to the first content management protocol.

For example, when the ODRL client 12 requests a content from the XrMLcontent server 22 it sends an ODRL based license request to thetranslation server 52. The translation server 52 sends a XrML basedlicense request to the XrML license server 20. The XrML license server20 returns an XrML license for accessing the requested XrML content. Thetranslation server 52 mediates this XrML license into an ODRL basedlicense and returns this to the ODRL client 12.

The ODRL client 12 sends an ODRL based content request, including theODRL based license or digital certificate, to the translation server 52.The translation server 52 mediates this ODRL based content request andencapsulated ODRL based license into a XrML based content request and anencapsulated XrML based license. The XrML content server 22 returns thecontent with an associated rights statement to the translation server 52in accordance with the XrML content management protocol. The translationserver 52 mediates the XrML content and associated rights statement tothe content and associated rights statement according to the ODRLcontent management protocol. In some embodiments, authorization may berequired from the content provider prior to mediation or translation.

The ODRL client 12 consumes the content according to the restrictions ofthe rights statement and sends usage reports to the translation server52 in accordance with the ODRL content management protocol. Thetranslation server 52 mediates the ODRL based usage reports to XrMLbased usage reports and forwards the XrML based usage reports to theXrML license server 20.

The process for mediating a XrML client 18 request for content from theODRL content server 16 is a reflection of the above described process.In general, the translation server 52 or mediation component maps,mediates, or translates requests and responses according to one contentmanagement protocol to requests and responses in another contentmanagement protocol.

The ODRL license server 14, the ODRL content server 16, the XrML licenseserver 20, the XrML content server 22, and the translation server 52 maybe computer programs or applications which may run on a general purposecomputer system. The ODRL client 12 and the XrML client 18 are computerprograms or applications which, for purposes of understanding thisdisclosure, may be assumed to run on general purpose computer systems.In some embodiments the ODRL client 12 and the XrML client 18 mayexecute on wireless mobile devices. General purpose computer systems arediscussed in greater detail herein after.

FIG. 2 depicts the translation server 52 mediating between XrML basedand ODRL based content management and access systems, but it iscontemplated that the translation server 52 is able to map between anytwo or more content management protocols or DRM protocols. The presentillustration contemplates other DRM systems and protocols.

Turning now to FIG. 3, an alternate DRM integrated access system 80 isdepicted. A DRM client manager 82 is in communication with the ODRLlicense server 14, the ODRL content server 16, the XrML license server20, the XrML content server 22, and a DRM swap server 84. The DRM swapserver 35 may be an application or computer program which may execute,for example, on a general purpose computer system. The DRM clientmanager 82 is an application or computer program which, for purposes ofunderstanding this disclosure, may be considered to run on a generalpurpose computer system. In some embodiments the DRM client manager 82may run on a mobile wireless device.

When the DRM client manager 82 is deployed on a mobile wireless device,memory resources may be limited and may be unable to store and operateboth the ODRL client 12 and the XrML client 18. The DRM swap server 84is in communication with a database 86 which contains the ODRL client 12and the XrML client 18 which the DRM client manager 82 requires toaccess and consume ODRL based content and XrML based content,respectively.

When the DRM client manager 82 needs to access ODRL based content, theDRM client manager 82 first requests the DRM swap server 84 to read theODRL client 12 from the database 86 and to send the ODRL client 12 tothe DRM client manager 82. The DRM client manager 82 loads the ODRLclient 12 into the memory of the device, such as, but not limited to, amobile wireless device. The ODRL client 12 then, under control of theDRM client manager 82, conducts a standard ODRL content access session.

When the DRM client manager 82 needs to access XrML based content, theDRM client manager 82 first requests the DRM swap server 84 to read theXrML client 18 from the database 86 and to send the XrML client 18 tothe DRM client manager 82. The DRM client manager 82 loads the XrMLclient 18 into the memory of the device. The XrML client 18 then, undercontrol of the DRM client manager 82, conducts a standard XrML contentaccess session.

The DRM client manager 82 determines the DRM protocol required to accessthe ODRL or XrML content servers 16 and 22 either by having the DRMprotocol designated to the DRM client manager 82, such as by user input,or by discovering the DRM protocol through a handshaking operation withthe ODRL or XrML content servers 16 and 22. The DRM client manager 82may be considered to contain within it one of the ODRL client 12 and theXrML client 18, which the DRM client manager 82 receives from the DRMswap server 84.

In some embodiments the DRM client manager 82 may first check to see ifthe needed DRM client, one of the ODRL client 12 and the XrML client 18,is already in memory before fetching and loading, thereby saving timeand communication resources if the needed DRM client, either the ODRLclient 12 or the XrML 18, is already located in memory.

While FIG. 3 depicts the database 86 containing the ODRL client 12 andthe XrML client 18, it is contemplated that the database 86 may containother DRM clients or content management clients to enable the DRM clientmanager 82 to interact with other DRM systems or content managementsystems. Additionally, it is contemplated that the DRM client manager 82may request portions of the DRM client, one of the ODRL client 12 andthe XrML client 18, or content management clients, for example portionsof the ODRL client 12 and portions of the XrML client 18, when theseportions are needed.

For example, when the DRM client manager 82 requests an ODRL basedlicense, the DRM client manager 82 requests the ODRL based licenseportion of the ODRL client 12 from the DRM swap server 84. The DRMclient manager 82 receives and loads the ODRL based license portion ofthe ODRL client 12 into memory. The DRM client manager 82 executes thisODRL based license portion of the ODRL client 12. The DRM client manager82 requests the ODRL license from the ODRL license server 14. The DRMclient manager 82 receives the ODRL based license from the ODRL licenseserver 14.

When the DRM client manager 82 requests the ODRL content, the DRM clientmanager 82 requests the ODRL based content server portion of the ODRLclient 12 from the DRM swap server 84. The DRM client manager 82 loadsthe ODRL based content server portion of the ODRL client 12 into memory.The DRM client manager 82 executes the ODRL based content server portionof the ODRL client 12. The DRM client manager 82 requests the contentfrom the ODRL content server 16. The DRM client manager 82 receives theODRL based content from the ODRL content server 16.

When the DRM client manager 82 consumes the ODRL based content, the DRMclient manager 82 requests the ODRL based content consumption portion ofthe ODRL client 12 from the DRM swap server 84. The DRM client manager82 loads the ODRL based content consumption portion of the ODRL client12 into memory. The DRM client manager 82 executes the ODRL basedcontent consumption portion of the ODRL client 12. The DRM clientmanager 82 consumes, or plays back, the ODRL based content and sends ausage report to the ODRL license server 14.

This example of segmented ODRL client 12 execution is only exemplary.Other segmentations or partitions, at either a coarser or a finersegmentation granularity, of the DRM clients, for example either theODRL client 12 or the XrML client, or content management clients may beemployed.

Wireless mobile devices, such as mobile phones, may be well suited tothe DRM integrated access system 80. Wireless mobile devices may havelimited memory resources, and emerging third generation wirelesstechnologies now support data channels featuring relatively highbandwidth adequate to transmit in whole or in segments DRM clients, forexample either the ODRL client 12 or the XrML client 18, or contentmanagement clients. In one embodiment of the DRM integrated accesssystem 80 the DRM client manager 82 resides on a wireless mobile device.

Turning now to FIG. 4, a system 120 for on-demand loading of computerprograms into a wireless mobile device 121 is depicted. The system 120provides on-demand loading of any computer programs or applications andis not limited to on-demand loading of the digital rights management orcontent management client applications discussed earlier. The wirelessmobile device 121 is in communication with a wireless network 124. Thewireless mobile device 121 contains an application swap client 122. Thewireless network 124 is in communication with a public switchedtelephone network (PSTN) 126. The PSTN 126 is in communication with anapplication swap server 128. The application swap server 128 is incommunication with an applications database 130.

The application swap server 128 may be a computer program or applicationwhich may execute on a general purpose computer system. The applicationswap client 122 may be a computer program or application which mayexecute on the wireless mobile device 121.

The wireless mobile device 121 may need to execute a computer program orapplication which is not loaded in memory. In this case, the applicationswap client 122 may interwork with the application swap server 128 todownload the application from the applications database 130 to thememory of the wireless mobile device 121. The wireless network 124 andthe PSTN 126 provide the communications link between the applicationswap client 122 and the application swap server 128. The wireless mobiledevice 121 may then execute the application. It is contemplated that thesystem 120 may be employed to download complete applications or segmentsof applications. In one embodiment, the system 120 may be operable fordownloading segments of applications. For example, a completeapplication may be executed by downloading a first segment of theapplication, executing the first segment of the application, downloadinga second segment of the application, executing the second segment of theapplication, and so on until the last segment of the application isdownloaded and executed.

The wireless network 124 may comprise a transceiver in wireless radiocommunication with the wireless mobile device 121, a bridge node linkingto the PSTN 126, such that the transceiver is in communication with thebridge node. The bridge node may link the wireless network to a packetdata network (PDN), the PDN may be in communication with the applicationswap server 128, and the wireless mobile device 121 may be incommunication with the application swap server 128 via the wirelessnetwork 124 and the PDN.

In one embodiment, a base transceiver station (BTS) 132 is in radiocommunication with the application swap client 122, a mobile switchingcenter (MSC) 134 bridges the wireless network 124 to the PSTN 126, and abase station controller (BSC) 136 links the BTS 132 with the MSC 134.

In another embodiment, the BTS 132 is in radio communication with thewireless mobile device 121, a gateway global packet radio system supportnode (GGSN) bridges the wireless network 124 to the PDN, a base stationcontroller (BSC) 136 links the BTS 132 to a serving global packet radiosystem support node (SGSN), and the SGSN is in communication with theGGSN.

Other wireless network topologies are also possible. The construction ofwireless networks is well understood by those skilled in the art. Thesystem 120 employs the wireless network 124 merely as a link between thewireless mobile device 121 and the application swap server 128.

Turning now to FIG. 5, a method for on-demand loading of computerprograms or applications into the wireless mobile device 121 isdepicted. At block 200, the method determines whether the applicationsegment is loaded, and whether authentication has been received. Wherethe application segment has not been loaded, but is authenticated, theprocess proceeds to block 202 where the appropriate application segmentis fetched. The process proceeds to block 204 where the applicationsegment is loaded into memory. The process proceeds to block 206 wherethe application segment is executed. If, at block 200, the appropriateapplication segment is determined to be loaded already, the processingproceeds to block 206, thus bypassing the fetch and load processingblocks 202 and 204 respectively.

From block 206 the process proceeds to block 208 where the process exitsif the application is complete. If the application is not complete, theprocess proceeds to block 202 and the fetch, load, and execute cycle ofblocks 202, 204, and 206 are repeated.

This process permits nearly any computer program or application to beexecuted on the application swap client 122. Alternate processes may beemployed for applications that do not tolerate being segmented.

Turning now to FIG. 6, an alternate DRM integrated access system 250 isdepicted. A multiprotocol content server 252 serves the content to theODRL client 12 and to the XrML client 18 according to the contentmanagement protocol suited to each device. Thus, when the ODRL client 12requests content from the multimode content server 252, themultiprotocol content server 252 accepts the ODRL based license embeddedin the request and returns the content according to the ODRL protocol.When the XrML client 18 requests content from the multiprotocol contentserver 252, the multiprotocol content server 252 accepts the XrML basedlicense embedded in the request and returns the content according to theXrML protocol.

While FIG. 6 depicts ODRL and XrML based devices and license servers,the DRM integrated access system 250 is contemplated to interwork withother content management protocols as well. The multiprotocol contentserver 252 may be a computer program or application which may beexecuted on a general purpose computer.

The systems described above may be implemented on any general-purposecomputer with sufficient processing power, memory resources, and networkthroughput capability to handle the necessary workload placed upon it.FIG. 7 illustrates a typical, general-purpose computer system suitablefor implementing one or more embodiments disclosed herein. The computersystem 380 includes a processor 382 (which may be referred to as acentral processor unit or CPU) that is in communication with memorydevices including secondary storage 384, read only memory (ROM) 386,random access memory (RAM) 388, input/output (I/O) 390 devices, andnetwork connectivity devices 392. The processor may be implemented asone or more CPU chips.

The secondary storage 384 is typically comprised of one or more diskdrives or tape drives and is used for non-volatile storage of data andas an over-flow data storage device if RAM 388 is not large enough tohold all working data. Secondary storage 384 may be used to storeprograms which are loaded into RAM 388 when such programs are selectedfor execution. The ROM 386 is used to store instructions and perhapsdata which are read during program execution. ROM 386 is a non-volatilememory device which typically has a small memory capacity relative tothe larger memory capacity of secondary storage. The RAM 388 is used tostore volatile data and perhaps to store instructions. Access to bothROM 386 and RAM 388 is typically faster than to secondary storage 384.

I/O 390 devices may include printers, video monitors, liquid crystaldisplays (LCDs), touch screen displays, keyboards, keypads, switches,dials, mice, track balls, voice recognizers, card readers, paper tapereaders, or other well-known input devices. The network connectivitydevices 392 may take the form of modems, modem banks, ethernet cards,token ring cards, fiber distributed data interface (FDDI) cards, andother well-known network devices. These network connectivity 392 devicesmay enable the processor 382 to communicate with an Internet or one ormore intranets. With such a network connection, it is contemplated thatthe processor 382 might receive information from the network, or mightoutput information to the network in the course of performing theabove-described method steps. Such information, which is oftenrepresented as a sequence of instructions to be executed using processor382, may be received from and outputted to the network, for example, inthe form of a computer data signal embodied in a carrier wave.

The processor 382 executes instructions, codes, computer programs,scripts which it accesses from hard disk, floppy disk, optical disk(these various disk based systems may all be considered secondarystorage 384), ROM 386, RAM 388, or the network connectivity devices 392.

Content providers want to secure their economic interests and protecttheir content rights. Content consumers want to access contentconveniently. It is not in the interests of either content providers orcontent consumers that incompatible DRM protocols create barriersbetween them. The several embodiments described above provide, forexample, useful techniques for overcoming these DRM protocol barriersand connecting content consumers with content providers.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods may beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein, but may be modified withinthe scope of the appended claims along with their full scope ofequivalents. For example, the various elements or components may becombined or integrated in another system or certain features may beomitted, or not implemented.

Also, techniques, systems, subsystems and methods described andillustrated in the various embodiments as discreet or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown as directly coupled or communicating with each othermay be coupled through some interface or device, such that the items mayno longer be considered directly coupled to each but may still beindirectly coupled and in communication with one another. Other examplesof changes, substitutions, and alterations are ascertainable by oneskilled in the art and could be made without departing from the spiritand scope disclosed herein.

1. A system for wirelessly accessing content and applications to play oruse the content, comprising: a mobile device configured to request thecontent, comprising: a memory configured to store less than all of aplurality of applications at a time, wherein each of the plurality ofapplications is configured to play or use the content according to acorresponding one of a plurality of content management protocols, andwherein the plurality of applications comprises an applicationconfigured to play or use content according to the open digital rightslanguage protocol and an application configured to play or use contentaccording to the extensible rights markup language protocol; and acontent consumption component configured to play or use the contentusing one of the plurality of applications that is stored in the memory;a swapping component configured to receive a request for any one of theplurality of the applications and to communicate the requested one ofthe plurality of applications to the mobile device for storage in thememory and use by the content consumption component; and a contentcomponent configured to receive a request for the content from themobile device and to communicate the content to the mobile deviceaccording to a first of the plurality of content management protocols,wherein the swapping component receives a request for and communicates afirst of the plurality of applications to the mobile device for storagein the memory and use by the content consumption component to play oruse the content according to the first of the plurality of contentmanagement protocols.
 2. The system of claim 1, wherein the mobiledevice further comprises: an application manager configured to requestone of the plurality of applications not stored in the memory from theswapping component, and wherein the swapping component provides therequested one of the plurality of applications to the mobile device inresponse to the request from the application manager.
 3. The system ofclaim 2, wherein the application manager is further configured todetermine which of the plurality of applications to request in order toaccess the content on the content component by one of receiving adesignation of the one of the plurality of applications or discoveringthe one of the plurality of applications through communication with thecontent component.
 4. The system of claim 1, wherein the memory isconfigured to only store one of the plurality of applications at a time.5. The system of claim 1, further comprising: a second content componentconfigured to receive a second request for second content from themobile device and to communicate the second content to the mobile deviceaccording to a second of the plurality of content management protocols,wherein the swapping component provides a second of the plurality ofapplications to the mobile device to present the second content with thecontent presentation device according to the second of the plurality ofcontent management protocols.
 6. The system of claim 1, wherein thecontent is further defined to be selected from at least one of the groupconsisting of text, audio, video, music, audio/video, and encryptedcontents.
 7. A method for providing content management clients to amobile device to access and play content secured according to differentcontent management protocols, comprising: receiving by a swappingcomponent a request from the mobile device for one of a plurality ofcontent management clients, wherein each of the different contentmanagement clients is configured to play content according to acorresponding one of the different content management protocols, andwherein the plurality of content management clients comprises a contentmanagement client configured to play content according to the opendigital rights language protocol and a content management clientconfigured to play content according to the extensible rights markuplanguage protocol; obtaining by the swapping component the requestedcontent management client from a component that maintains the differentcontent management protocols; and communicating by the swappingcomponent the requested content management client to the mobile device,wherein the mobile device has limited memory resources and is onlycapable of storing less than all of the plurality of content managementclients at a time.
 8. The method of claim 7, wherein the mobile deviceis only capable of storing one of the plurality of content managementclients at a time.
 9. The method of claim 7, wherein the content isselected from at least one of the group consisting of text, audio,video, music, audio/video, and encrypted contents.
 10. The method ofclaim 7, wherein the plurality of content management clients areprograms.
 11. The method of claim 7, further comprising: receiving bythe swapping component a request from the mobile device for a portion ofone of the plurality of content management clients; obtaining by theswapping component the requested portion of the one of the plurality ofcontent management clients from a component that maintains the differentcontent management protocols; and communicating by the swappingcomponent the requested portion of the content management client to themobile device.
 12. A method for providing content management clients toa mobile device to access and use content secured according to differentcontent management protocols, comprising: receiving by a swappingcomponent a request from the mobile device for one of a plurality ofcontent management clients, wherein each of the different contentmanagement clients is configured to use content according to acorresponding one of the different content management protocols, andwherein the plurality of content management clients comprises a contentmanagement client configured to use content according to the opendigital rights language protocol and a content management clientconfigured to use content according to the extensible rights markuplanguage protocol; obtaining by the swapping component the requestedcontent management client from a component that maintains the differentcontent management protocols; and communicating by the swappingcomponent the requested content management client to the mobile device,wherein the mobile device has limited memory resources and is onlycapable of storing less than all of the plurality of content managementclients at a time.